################################################################################
# Translation Guide                                                            #
################################################################################
#
# I.    @title tag MUST appear in the first line of the file. This is the name
#       that appear in the Preference window.
#       Please use the name of the language in the language itself.
#       Example for French:
#         @title: "Franais"
#
# II.   @author and @contact tags are OPTIONAL, but if present MUST follow the
#       @title tag immediately. These tags are credit information that will 
#       display in the Preference window.
#       The @contact tag MUST start with "http://", "https://" or "mailto:".
#
#
# III.  The file MUST be encoded in UTF-8. You can save with the BOM, it might
#       even be safest. If a file is not recognised as UTF-8 it will mangle
#       the interpretation of all the language files.
#
# IV.   The filename MUST be saved with ASCII range characters. SketchUp's Ruby
#       version, 1.8, does not handle files with non-ASCII characters.
#
# V.    Please name your .lang file using the language code SketchUp reports
#       for that language. This will ensure that Vertex Tools tries to load
#       the language which match the current SketchUp language.
#       A list of language codes can be found here:
#         https://developers.google.com/sketchup/docs/ourdoc/sketchup#get_locale
#       Example for French language file: "fr.lang"
#       If you can not find the language listed, use a language code from
#       ISO 639-1.
#         http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes
#
# VI.   Please include your name, contact info and the date the file was last 
#       revised.
#
# VII.  Except for the title, the order of the file does not matter.
#
# VIII. Except for the first line, you can add comments anywhere you like.
#
# XI.   The % symbol is a special character. It represents a variable and MUST
#       be included. If you need to add a percent symbol to the strings you
#       can do so by using a double percent sign: %%
#       Example:
#         "Hello %% World" becomes "Hello % World"
#       All the strings are sprintf formatted.
#       For more info: http://ruby-doc.org/core/classes/Kernel.html#M005962
#
# X.    Another set of variables are @@n - where n represent a number. These are
#       used by webdialogs. When present in the original string they MUST appear
#       in the translated string.
#       Example:
#         "Hello @@1 World" becomes "Hello 123 World"
# 
# XI.   Do not insert line breaks into strings. The strings must appear on a
#       single line.
#
# XII.  To check for missing string you can open the Ruby Console and type
#       TT_Vertex::S.check
#       This will compare all the language files against the Norwegian file
#       and list out any missing strings for all the languages.
#
################################################################################


################################################################################
# Translation Tips                                                             #
################################################################################
#
# I.    Do not literally translate the words, translate the meaning.
#
# II.   If possible, use the same terms used in SketchUp if SketchUp exist in
#       the target language. Look to other 3d modelling and graphic software
#       products and find out what the norm is.
#
# III.  Great repository of translations terms in Microsoft's products.
#       http://msdn.microsoft.com/en-gb/goglobal/bb688105.aspx
#
# IV.   Look for guidance for translating to your own language. Often you can
#       find guides provided by Open Source projects.
#         Norwegian Guidelines:
#         http://i18n.skolelinux.no/retningslinjer.html
#
################################################################################